Debt Recovery
The jobs involved in debt recovery are:
Debt Recovery Job
After an account
In the Cloud Monetisation Platform, a billing entity that can be used to manage payments on one or more subscriptions or payments for services. An account can hold details such as payments or invoices. has been through the credit control process and the operator is still unable to recover the unpaid debt, the collection of that debt can be assigned to a third party Of software; a reusable component developed to be either freely distributed or sold by an entity other than the original vendor of the development platform. known as a Debt Recovery Agency (DRA Debt Recovery Agency. Companies that specialise in collecting debt when the original creditor cannot get the arrears repaid.).
The Debt Recovery job populates a number of database tables with debt recovery information of accounts that have particular account types. These account types are specific to the debt recovery process and are typically on a credit control procedure.
This job generates a batch that includes accounts to be referred to a DRA. The batch includes details such as:
- The amount of money to recover from the customer In the context of the Cloud Monetisation Platform, an individual or organisation who has signed an agreement to take goods and services from a service provider. A customer receives a bill associated with one or more subscriptions, and can be a single end user or a large company with many subscriptions assigned to one agreement.
- The amount that was recovered since the last extract
- Contact information such as postal address, email address and telephone numbers
The extract also contains header information that indicates the following to the debt recovery agency (DRA):
- The source company
- The position of the DRA in the recovery process - for example are they the first or second DRA to deal with this customer.
- The name of the DRA
- The total of the individual balances to recover
Associated jobs handle the response file that comes back from the DRA.
This job doesn't depend directly on any other jobs being run before it and is typically run on a schedule that is agreed with the DRA. Usually a separate instance of the job is run for each account type. These jobs cannot be run at the same time.
The different account types must be processed in the correct order. Running the job changes the account types of accounts. After the job runs, a workflow is raised against each account included in the extract. This workflow is typically configured with an Account Type Movement action, which changes the account type. This causes problems if the jobs are run in the incorrect order.
For example, suppose the Credit Control Process has put an account onto account type 701. This account is picked up by the Debt Recovery Agency Extract job and after account type 701 is processed, a workflow is raised against the account to move the account onto account type 702. The job for extracting account type 702 must be run before account type 701. This is because the workflow raised against Type 701 has an Account Type Movement action on it that changes the account type to 702. So by extracting Type 702 first, you avoid the risk of an account being included in both extracts.
On successful completion of the job, the following database tables are populated:
- Interface Batch Header
- Interface Batch Detail
- DRA Extract Batch Header
- DRA Extract Batch Detail
This is a scheduled job and typically runs once a month.
The following daemon A computer program that runs as a background process, rather than being under the control of an interactive user. is associated with Debt Recovery:
| Daemon | Details | ||
|---|---|---|---|
| Extract Debt Recovery To Generic Format | This daemon creates and encrypts generic CMP files, which are available for conversion to third party format. | ||
The following probes can be run against the Debt Recovery job:
| Name | Type | Description | ||
|---|---|---|---|---|
| Debt Recovery Extract Completed | Alert | Alert probe that returns the number of files produced by the Debt Recovery Extract daemon today. A value of zero indicates that no outbound files were produced and an alert will be sent to the recipients configured for this probe. | ||
| Debt Recovery Extract Completed | SLA | SLA probe that returns the number of files produced by the Debt Recovery Extract daemon today. A value of zero indicates that no outbound files were produced and the SLA has been breached. Because this is an SLA probe, no email alert is issued. | ||
| Debt Recovery Batch Completed | Alert probe that returns the number of times the Debt Recovery job has run today. A value of zero indicates that the job has not run today and an alert will be sent to the recipients configured for this probe. | |||
Relevant JSON schema A specification for JSON based format for defining the structure of JSON data.:
Debt Recovery Response Job
After an account has been through the credit control process and the operator is still unable to recover the unpaid debt, the collection of that debt can be assigned to a third party known as a Debt Recovery Agency (DRA). The DRA can provide feedback such as amount recovered and/or payment plans. When CMP Converged Monetisation Platform. The MDS Global product that supports customer care and billing for digital service providers. receives debt recovery response files, these are automatically detected by a dedicated daemon that creates a debt recovery response batch for each file received. This job is responsible for updating account details to reflect the debt recovery progress.
This job is automatically triggered whenever a new debt recovery response batch has been created.
The Debt Recovery Agency Response job processes the response files from the DRA that have been ingested into the database by the DRA Response Daemon. The job raises a workflow against each account contained in the response and adds some workflow notes containing data that was in the response file from the DRA. Configuration that maps the DRA > Response Code > Event Code and Event Type is contained in the Debt Recovery Agency and DRA Response Code Overrides database tables.
Any errors that arise - such as an invalid account number or an invalid response code - cause errors to be written to the Interface Batch Error file.
The key tables affected are:
- Interface Batch Header
- Interface Batch Detail
- DRA Response Header
- DRA Response Detail
- DRA Response Payment Plan Detail
The following daemons are associated with Debt Recovery Response:
| Daemon | Details | ||
|---|---|---|---|
| Load Debt Recovery Response From Generic Format | This daemon is collects and decrypts generic CMP files and creates CMP batches, which are available for processing into CMP by the appropriate batch job | ||
| Acknowledge Debt Recovery Response Receipt Of | This daemon generates an outbound acknowledgement of an inbound file being processed. | ||
The following probe In the Administration Console architecture, a mechanism which allows for the execution of predefined queries and for the comparison of the results of those queries against pre-configured targets. Probes can be reviewed and managed via the Admin Console.(s) can be run against the Debt Recovery Response job:
| Name | Type | Description | ||
|---|---|---|---|---|
| Debt Recovery Response Batch Completed | Alert probe that returns the number of times the Debt Recovery Response Job has run today. A value of zero indicates indicates the job has not run today. | |||
| Debt Recovery Response Batch Completed | SLA probe that returns the number of CMP configuration errors detected by the Debt Recovery Response job today. The SLA is breached if the number of errors is above the defined threshold. These type of errors can be resolved by amending CMP configuration. Because this is an SLA probe, no email alert is issued. | |||
| Debt Recovery Response Load Completed | Alert probe that returns the number of files received by the Debt Recovery Response Load daemon today. A value of zero indicates that no inbound files were received today and an alert will be sent to the recipients configured for this probe. | |||